Systems and methods for adaptive context-aware control of multimedia communication sessions

ABSTRACT

A system to adaptively control multimedia communication sessions includes a mediator unit in an intermediary communication position between two or more remote clients and a media infrastructure. The mediator unit includes a receiver, a transmitter and a control processor that controls the receiver and the transmitter. The mediator unit communicates remote clients across a communication network, where the first client initiates a communication session and the mediator unit assigns a unique session identifier to the communication message. Additional remote clients send join requests including the unique session identifier, and the mediator unit acts as a back-to-back user agent to pass messages between two remote clients of a two-client communication session. The control processor configured to execute predefined context-sensitive strategies including the number of remote clients in the communication session, bridging incompatible peer-to-peer communications, supporting multiple devices of a single remote client, and dynamic allocation of multipoint control unit resources.

BACKGROUND

Videoconferencing systems allow two or more locations to communicateacross duplex (i.e., simultaneous, two-way) audio and video channels.The availability of low cost, high capacity broadband services supportedby powerful processors capable of sophisticated compression algorithmshas led to the widespread use of videoconferencing in a wide variety ofcommunications—personal, business, education, government, etc.

A multipoint control unit (MCU) is a device that is used tointerconnect, or bridge, three or more remote clients (terminals,workstations, gateways, etc.) into one simultaneous videoconferencesession. among three or more remote points is possible by means of aMultipoint Control Unit (MCU). This is a bridge that interconnects callsfrom several sources (in a similar way to the audio conference call).

The MCU can be located at an endpoint of a local area network (LAN). TheMCU can collect bandwidth capability data for each of the remote clientsof a videoconference. The MCU then configures the session to meet thecapability of the least powerful remote client to assure that thevideoconference is of the best quality for each participant.

An MCU can be a stand-alone device or it can be embedded into dedicatedvideoconferencing units. At a high-level, the MCU can be viewed asincluding two components, a single multipoint controller (MC), and oneor more multipoint processors (MP), sometimes referred to as the mixer.

The MC controls the conferencing while it is active on the signalingplane—managing conferencing creation, endpoint signaling andin-conferencing controls. The MC can negotiate parameters with everyendpoint in the network and control conferencing resources. The MP(s)operate on the media plane and receive media from each endpoint, andthen generates output streams from each endpoint and redirects theinformation to other endpoints in the conference.

Digital compression of audio and video streams in real time is performedby a coder/decoder (codec). The compressed digital stream can besubdivided into labeled packets, which are then transmitted through anelectronic communication network under a known protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B depict a system in accordance with some embodiments;

FIG. 2 depicts a flow diagram of a bridging process in accordance withsome embodiments;

FIGS. 3A-3C depict a flow diagram of an allocation process in accordancewith some embodiments; and.

FIG. 4 depicts a flow diagram of a device switch process in accordancewith some embodiments.

DETAILED DESCRIPTION

In accordance with embodiments, systems and methods provide acontext-aware framework for adaptively controlling multimediacommunication sessions. Embodying systems and methods provide a mediatorunit that is an intermediary entity located between a remote client andthe underlying media infrastructure. The mediator unit mediatescommunication between the remote clients and the media infrastructure.

FIG. 1A depicts system 100 during a two-client communication phase inaccordance with some embodiments. System 100 can include mediator unit110 that can include receiver 112, transmitter 118, and controlprocessor 116. In some implementations, receiver 112 and transmitter 118can be separate units within mediator unit 110 as depicted. In otherimplementations, the receiver and transmitter can be structured as atransceiver. The receiver and transmitter are operated under the controlof control processor 116.

For purposes of description, during the two-client communication phasesystem 100 includes two remote clients—client1 122 and client2 126.However, system 100 is not limited to a two-client communicationsession, and other numbers of remote clients can be implemented. Inaccordance with implementations, the remote clients transmitcommunication messages to the mediator unit, which then routes themessages to the proper destination(s). In conventional communicationsystems, an intermediary entity merely acts as a proxy to simplyexchange communication messages between remote clients. However,embodying mediator units have a proactive role in the process and managecommunication sessions based on contextual information regarding theremote clients and media infrastructure. The contextual information caninclude, but is not limited to, network bandwidth, numbers of clients,codecs, and content being communicated. By way of example, contextualinformation can also include the nature of a video conference's contentcan be used by the mediator to process and manage a communicationsession. For example, if the video conference is sharing a video of amanufacturing part inspection versus video conferencing of individuals,different codecs or parameters can be chosen by the mediator to optimizethe session. Another example of contextual information that the mediatorunit can use is if one client is streaming a PowerPoint presentation,the mediator could potentially automatically detect long static imagesand switch to a much lower frame rate. The frame rate can then beincreased by the mediator when dynamic images are later detected (e.g.,video playback, or participant interaction). In another non-limitingexample of contextual information used by the mediator, the mediatorunit's proactive role can include, but is not limited to, (1)automatically convert a peer-to-peer connection to an MCU connection;(2) automatically perform media transcoding when the clients supportdifferent codes; and (3) allow a user to switch devices without droppingcurrent communication session. Embodying MCUs make these proactive roledecisions based on contextual cues, which cannot be done by aconventional MCU.

Mediator 110 accesses various contextual knowledge regardingparticipating communication entities, such as the server(s) supportingthe communication network, the remote clients, the surrounding networkenvironment, etc. The information is collected and stored at themediator unit. Some of it is statically stored, such as networktopology, but some is dynamically collected from the environment (e.g.network bandwidth), or from the user client (e.g. number of clients inthe session, locations of the clients). The MCU uses knowledge includedin the client's session description protocol (SDP), such as client's IPaddress, port number, media codec, etc. This contextual knowledge isused to provide adaptive, flexible, intelligent, context-awarecommunications without requiring complex modifications to the remoteclients. In accordance with embodiments, because the MCU has suchintelligence built in, the clients are freed from certain networkconnection chores and overhead—for example, in embodying systems clientsdo not need to handle redial when switching devices, calling a differentnumber when more than two participants join the communication session,or switch codecs when clients on incompatible platforms (e.g., VP8 videocompression, virtual synchrony systems, H264 compression format, etc.)join the communication session.

By having knowledge about the number of clients in each communicationsession, the media codecs supported by each client at the mediator,system resource allocation of the MCU and/or media transcoder can beoptimized. Each client supports a predetermined set of media codecs.When the client calls into the session, it provides its list ofsupported codecs in their SDP.

The mediator unit reviews the supported codecs of the clients in thecommunication session to identify a common codecs among clients. If theyall share at least one codec, mediator exchange SDP by using the commonone, so transcoder is not needed. If there is no common codecs, themediator will allocate transcoder to bridge the video streaming.Further, the mediator can have its own list of supported codecs, whichcan include the client codecs.

Mediator 110 is configured to detect changes in the remote clientaddress (e.g., reconnect to the session using a different user ID (e.g.SIP address), reconnection at another URL, etc.) and/or changes in thedevice instrumentation itself (e.g., from a terminal to a smart phone,vice versa, and any other instrumentation change).

The mediator unit provides seamless mobility support of thecommunication session when a remote client changes location from oneplace to another. As the remote client changes location, the networkaddress used for communication can be changed. Under conventionalsystems if each client is directly connected to the other, the sessionhas to be terminated and be re-established with a new address. Accordingto embodiments, an embodying mediator unit allows remote clients to keepa communication session active even though the network address ischanged. Embodying mediator units maintain the session state, as opposedto the conventional approach of the session state being maintained oneach client side. When a user drops connection, the session/client stateis still maintained by the mediator. Accordingly, when the user re-joinsthe session the state will be recovered by the mediator. Under thisprocess, other participants in the same session are not impacted.

The mediator unit provides a smooth user experience by routing messagesto the new address and/or changing to communication protocols and/orformats suitable for the new remote client device without droppingcurrent sessions.

In accordance with embodiments, the basic unit of communication isdefined as a communication session started by one, or more, of remoteclients 122, 126, 128. At the start of a communication session a uniquesession ID (SID) is assigned by the mediator unit when it receives a newsession request from the client(s). This unique SID is used to identifythe session by all participating clients. Each remote client who wantsto join the communication session sends a join request with the sessionID to mediator unit 110. Control processor 116 within the mediator unitprocesses the join requests, and messages. The actions taken by thecontrol processor is based on contextual knowledge. In accordance withembodiments, this contextual knowledge can be of the participatingclients, or content of the message, or other contextual information. Therelevancy of the information's content is determined based on the usecase.

Receiver 112 receives communications messages from the remote client(s).Receiver 112 parses SID information of the communication and identifiesthe communication session to which the communication message belongs.Control processor 116 executes algorithms of predefinedcontext-sensitive strategies to determine what action the mediator unitis to undertake in handling the communication message. Based on thedetermination results of the control processor, transmitter 118transmits appropriate responses and/or requests to the remote client(s).

FIG. 1B depicts system 150 that includes client3 128, as a third clientjoining the session depicted in FIG. 1A, to create a multi-clientcommunication phase in accordance with some embodiments. FIGS. 1A-1Billustrate a simple example of how communication requests, in the formof SIP messages, from remote client(s) are processed differently by themediator unit based on different contexts. For purposes of this example,the context is simply the number of clients. In the beginning (phase 1)(FIG. 1A) there are two clients in the session. Later a third clientjoins the session (phase 2) (FIG. 1B). During the second phase, wherefor purposes of explanation the context is based on the number ofparticipants, the mediator automatically switch to a MCU session. Forexample, in a session identified “SID”, all clients send their SIPmessages to the mediator unit with “SID” as part of the destination SIPaddress. By parsing the SIP address, the mediator knows that the clientsparticipate in the session identified by “SID.” During phase 1, becausethere are only two clients in the session, they support the same mediacodec. Hence, the mediator unit performs the role as a back-to-back useragent to pass messages through to each of the two remote clients in thesession.

Later, third client (client3 128) joins the same session by sending SIPmessages with the same “SID”, the mediator determines that there aremore than two clients in the same session (now in phase 2). Therefore,the mediator unit directs all SIP messages with SID “SID” in thedestination SIP address to MCU 130. The MCU then handles communicationbetween the three or more remote clients participating in the session.According to embodiments, these strategies adaptively mediatecommunication sessions by using different kinds of contextual knowledgein the context of SIP-based communication.

The predefined context-sensitive strategies implemented by controlprocessor 116 can include, but are not limited to, bridging incompatiblepeer-to-peer (P2P) communication; dynamic allocation of MCU resourcesbased on the number of participants; and supporting multiple devices ofa remote client.

FIG. 2 depicts a flow diagram of bridging process 200 for bridgingincompatible P2P entities in accordance with some embodiments. Bridgingprocess 200 is applicable in peer-to-peer sessions whenever theincompatibility of supported media codec between peers is detected. Inaccordance with embodiments, the session description protocol (SDP)negotiation will be modified by mediator unit 110 to use a mediatranscoder. A remote client calls into a P2P session, step 210, via themediator unit. The mediator unit sends an INVITE with an empty SDP, step220, to get a response from the second remote client. This step is doneinstead of forwarding the INVITE request with the first remote client'sSDP (sdp1). The second remote client responds with its own SDP (sdp2),step 230.

The mediator parses the content of the two SDP messages it has received(the INVITE from remote client 1, and the response from remote client2), to check the compatibility (and/or whether there is anincompatibility) between the two remote clients, step 240. If anincompatibility between the two remote clients is uncovered (i.e., acommon media codec cannot be found), the mediator sends a modifiedresponse, step 250, to the first remote client.

This modified response includes the media transcoder's media informationas the SDP answer. Meanwhile, the mediator sends the ACK to the secondremote client, step 260, with the media transcoder's media information.In this way, the P2P communication between the two remote clients isbridged, step 270, using the media transcoder, without the mediatranscoder involved in the communication initialization.

FIGS. 3A-3C depict a flow diagram of allocation process 300 forallocating an MCU for video conferencing in accordance with someembodiments. Allocation process 300 relates to dynamic allocation of MCUresources based on the number of participants in a video conferencingsession. In response to a first remote client of a given communicationsession calling in, step 310, the mediator unit can place the firstremote client on hold by responding with an SDP having a recvonlyattribute, step 315.

When a second remote client calls into the session, step 320, thesession can be converted into a P2P session by having the mediator unitforwarding requests/responses from one client to each other, step 325.In accordance with embodiments, with only two clients engaged in thecommunication session, the mediator unit performs the interchangebetween these clients.

Should a third remote client enter the session, step 330, the mediatorunit can allocate an MCU for the session. The mediator unit converts thesession to an MCU session, step 335. Mediator calls the API of the MCUto allocate a room, and get the room address that can be called in bythe client.

The MCU invites remote client 3 into this communication session throughthe mediator unit, step 340. The MCU invites remote client 1 into thiscommunication session through the mediator unit, step 344. The MCUinvites remote client 2 into this communication session through themediator unit, step 348.

In accordance with embodiments, the mediator unit forwardsrequests/responses from and between the three remote clients in thissession to the assigned MCU. In this way, MCU resources are reserved forthe sessions with more than two clients, and the mediator unitdynamically manages the MCU resources.

FIG. 4 depicts a flow diagram of device switch process 400 forsupporting multiple communication devices of a remote client inaccordance with some embodiments. In accordance with embodiments, shoulda remote client switch between active communication devices during acommunication session (e.g., from a mobile phone to a web browser on alaptop, vice versa, and any other instrumentation change), these devicescan be supported while maintaining the existing connection of thisremote client to the communication session. FIG. 4 depicts animplementation for a P2P session between two remote clients. However,embodiments are not so limited and communication sessions of more thantwo remote clients can be implemented.

At step 410, as described above remote client 1 and remote client 2enter into a communication session. In accordance with embodiments, whenone of the remote clients in this communication session switches fromone active device to another, step 420, the remote client does not needto hang up the previous connections and reconnect. Instead, the clientcan simply call into the same session with the same SIP address and witha different SDP. Because the mediator unit maintains a list of clientswho are in the session, the mediator unit can detect that this client isan existing participant by checking the session list. The mediator unitautomatically updates the session, by sending out a new INVITE with theclient's new device SDP to the peer (in a peer-to-peer session) or theMCU (in a conferencing session), step 422 The other remote client(s) ofthe communication session acknowledge this update to the session, step424. In this way, neither the client who switches the device, nor theother participant(s) in the session does any extra action to update thesession.

Embodying systems and methods provide smart resource allocation of theback-end media infrastructure. The mediator unit allocates an MCU if thenumber of participants for a session is more than two. The mediator unitdetects differences of codecs between the remote clients in thecommunication session. If there is a difference detected, the mediatorunit allocates the resources of a media transcoder. Because the mediatorunit detects whether codecs for the remote clients are compatible, theresources of an MCU and a media transcoder are not needed to beallocated for each communication session until an incompatibility isdetected. The mediator unit has the knowledge for participants or theirsupported codecs As noted above, because embodying mediators maintainthe session states with each client, the mediator is provided with theinformation about each participant and their supported codecs. Thisinformation can be stored on the memory or disk of the mediator deviceitself. By allocating resources (i.e., an MCU and/or media transcoder)to a remote communication session only when the number of participantsand/or incompatibility of participating remote clients require theresource allocation, the mediator unit reduces the resource consumptionof the back-end media infrastructure.

In accordance with embodiments, a generic framework is described thatcan be applied to any communication application. The adaptationstrategies described above are only a few possible use cases, and otheradaptation strategies can be developed based on the specific use casesand what kinds of contextual information are available in theapplication. For example, if network bandwidth information is available,the mediator can dynamically control each remote client's mediabandwidth by updating the desired transmission rate on the fly. Further,if a mediator unit has knowledge about the loads on multiple MCUs and/ortranscoders, the mediator unit can adjust a communication sessions toarchive the best performance of the video infrastructure.

In accordance with some embodiments, a computer program applicationstored in non-volatile memory or computer-readable medium (e.g.,register memory, processor cache, RAM, ROM, hard drive, flash memory, CDROM, magnetic media, etc.) may include code or executable instructionsthat when executed may instruct and/or cause a controller or processorto perform methods discussed herein such as a method for adaptivelycontrolling the allocation of back-end media infrastructure tocommunication sessions based on the number of participating remoteclients in the communication session and/or an incompatibility ofsupported media codecs between the participating remote clients, asdescribed above.

The computer-readable medium may be a non-transitory computer-readablemedia including all forms and types of memory and all computer-readablemedia except for a transitory, propagating signal. In oneimplementation, the non-volatile memory or computer-readable medium maybe external memory.

Although specific hardware and methods have been described herein, notethat any number of other configurations may be provided in accordancewith embodiments of the invention. Thus, while there have been shown,described, and pointed out fundamental novel features of the invention,it will be understood that various omissions, substitutions, and changesin the form and details of the illustrated embodiments, and in theiroperation, may be made by those skilled in the art without departingfrom the spirit and scope of the invention. Substitutions of elementsfrom one embodiment to another are also fully intended and contemplated.The invention is defined solely with regard to the claims appendedhereto, and equivalents of the recitations therein.

1. A system to adaptively control multimedia communication sessions, thesystem comprising: a mediator unit in an intermediary communicationposition between two or more remote clients and a media infrastructure;the mediator unit including a receiver, a transmitter and a controlprocessor, the control processor configured to execute instructions thatcause the control processor to control the receiver and the transmitter;the mediator unit configured to communicate with two or more remoteclients across a communication network, the communication network havinga server supporting operation of the communication network; a firstremote client configured to transmit a communication message on thecommunication network, the communication message initiating acommunication session; the receiver configured to receive thecommunication message from the communication network; the mediator unitis configured to assign a unique session identifier to the communicationmessage; additional remote clients configured to send join requests onthe communication network, each join request including the uniquesession identifier; and the mediator unit further configured to act as aback-to-back user agent to pass messages between two remote clients of atwo-client communication session.
 2. The system of claim 1, the receiverconfigured to parse session identifier information in the communicationmessage.
 3. The system of claim 1, the control processor configured toexecute predefined context-sensitive strategies to perform a decisionprocess.
 4. The system of claim 3, the predefined context-sensitivestrategies including at least one of the number of remote clients in thecommunication session, bridging incompatible peer-to-peercommunications, supporting multiple devices of a single remote client,and dynamic allocation of multipoint control unit resources.
 5. Thesystem of claim 1, the mediator unit further configured to applycontextual knowledge of the first and additional clients in a decisionprocess on whether a multipoint control unit is needed to conduct acommunication session having three or more remote clients.
 6. The systemof claim 1, the mediator unit configured to route communication messagesbetween the remote clients.
 7. The system of claim 1, the mediator unitconfigured to proactively process communication sessions based oncontextual information of the remote clients and media infrastructure.8. The system of claim 7, mediator unit configured to at least one ofconvert a peer-to-peer connection to a multipoint communication session,support a remote client to switch from a first communication device to asecond communication device while maintaining the current communicationsession, and perform media transcoding when remote clients of the samecommunication session support different codes.
 9. A method ofcontextually adapting a communication session, the method comprising:receiving at a mediator unit a first remote client first sessiondescription protocol invite call for a peer-to-peer session; sending anempty session description protocol invite message to a second remoteclient; receiving from the second remote client a second sessiondescription protocol message; the mediator unit parsing the content ofthe first session description protocol invite and the content of thesecond session description protocol; and the mediator unit initializingthe peer-to-peer session without a media transcoder involved in theinitialization.
 10. The method of claim 9, including the mediator unitdetermining if the result of the parsing step indicates anincompatibility between the first and the second remote clients.
 11. Themethod of claim 10 including, if an incompatibility is indicated, themediator unit sending a modified response to the first remote client anda acknowledge signal to the second remote client, wherein the modifiedresponse includes a media transcoder media information.
 12. A method ofallocating a multipoint communication unit for a video communication,the method comprising: receiving at a mediator unit a request from afirst remote client to join a video communication; the mediator unitplacing the first remote client on hold; receiving at the mediator unita request from a second remote client to join the video communication;and initiating the video communication by the mediator unit forwardingrequests and responses between the first and the second remote clientsin a peer-to-peer session.
 13. The method of claim 12, including placingthe first remote client on hold by responding with a session descriptionprotocol having a recvonly attribute.
 14. The method of claim 12,including: receiving a request from a third remote client to join thevideo communication; the mediator unit allocating a multipointcommunication unit to the video communication in response to the thirdremote client request; and the mediator unit converting the peer-to-peersession to a multipoint communication unit session.
 15. The method ofclaim 14, the multipoint communication unit inviting the first, thesecond, and the third remote client to the multipoint communication unitsession through the mediator unit.